Test Environment Mock-Up Tests
-
Behavior of the changed rquests
-
Testing the display of data that the RegAcc can generate itself
-
Verification Information
-
Registration date
-
-
Testing the display of data that the RegAcc cannot generate itself
-
Deadlines for de-delegation and deletion
-
Domain status
-
-
Testing of rudimentary process sequences
-
Changing the status and deadlines of a domain when valid or invalid verification information is provided
-
The mock-up is a model for achieving target states. No real transitions are simulated. Instead, domains are set to certain states and messages are generated. Messages may be sent more frequently than they will be later.
Test Scenarios
Input / Trigger (verificationResult > contact address trigger > domain name trigger) | Result | ||||||
---|---|---|---|---|---|---|---|
Domain name contains | Contact Address | VerificationResult | Request | Affected domains | Domain status (can be queried via RRI-INFO) | Deadlines | Messages |
any | NISpendingCreate | none | Domain CREATE | single | pendingCreate | none | none |
NISpendingCreate | any | none | Domain CREATE | single | pendingCreate | none | none |
any | any | none | Domain CREATE | single | connect | none |
ExamplesCopy
K/V domainStatusUpdate, verification not required
Copy
XML domainStatusUpdate, verification not required
|
any | NISconnect | none | Contact UPDATE | all | connect | none |
ExamplesCopy
K/V domainStatusUpdate, verification not required
Copy
XML domainStatusUpdate, verification not required
|
NISconnect | any | none | Domain CREATE | single | connect | none |
ExamplesCopy
K/V domainStatusUpdate, verification not required
Copy
XML domainStatusUpdate, verification not required
|
any | any | success | Contact UPDATE | all, “connect” for multiholder domains when all domain holders have been verified with ‘success’. If the domain has an unverified domain holder, the status of this domain remains unchanged. |
connect | none |
ExamplesCopy
K/V domainStatusUpdate, verification not required
Copy
XML domainStatusUpdate, verification not required
|
any | any | success | Domain CREATE | single | connect | none |
ExamplesCopy
K/V domainStatusUpdate, verification not required
Copy
XML domainStatusUpdate, verification not required
|
any | NISverificationRequired | none | Contact UPDATE | all | connect | VerificationDeadlineBeforeDedelegation VerificationDeadlineBeforeDeletion |
ExamplesCopy
K/V domainStatusUpdate, verification required
Copy
XML domainStatusUpdate, verification not required
|
NISverificationRequired | any | none | Domain CREATE | single | connect | VerificationDeadlineBeforeDedelegation VerificationDeadlineBeforeDeletion |
ExamplesCopy
K/V domainStatusUpdate, verification required
Copy
XML domainStatusUpdate, verification not required
|
any | any | failed | Contact UPDATE | all | connect | VerificationDeadlineBeforeDedelegation VerificationDeadlineBeforeDeletion |
ExamplesCopy
K/V domainStatusUpdate, verification required
Copy
XML domainStatusUpdate, verification not required
|
any | NISserverHold | none | Contact UPDATE | all | serverHold | VerificationDeadlineBeforeDeletion |
ExamplesCopy
K/V domainStatusUpdate, serverHold, verification required
Copy
XML domainStatusUpdate, serverHold, verification required
|
NISserverHold | any | none | Domain CREATE | single | serverHold | VerificationDeadlineBeforeDeletion |
ExamplesCopy
K/V domainStatusUpdate, serverHold, verification required
Copy
XML domainStatusUpdate, serverHold, verification required
|
any | any | failed | Domain CREATE | single | serverHold | VerificationDeadlineBeforeDeletion |
ExamplesCopy
K/V domainStatusUpdate, serverHold, verification required
Copy
XML domainStatusUpdate, serverHold, verification required
|
any | NISdelete | none | Contact UPDATE | all | free | none |
ExamplesCopy
K/V domainDelete
Copy
XML domainDelete
|
NISdelete | any | none | Domain CREATE | single | free | none |
ExamplesCopy
K/V domainDelete
Copy
XML domainDelete
|
any | any | any | Domain DELETE | single | redemptionPeriod | none | none |
To run through all test scenarios, the following sequence of orders can be used
Version: 5.0
Action: CREATE
Handle: DENIC-1000022-EXAMPLE-PERSON
Type: PERSON
Name: John Doe
PostalCode: 60596
City: Frankfurt
CountryCode: DE
EMail: john.doe@denic.de
Phone: +49.69272350
Address: NISpendingCreate
version: 5.0
action: CREATE
domain: domain-example-nsentry.de
holder: DENIC-1000022-EXAMPLE-PERSON
nsentry: domain-example-nsentry.de IN A 127.0.0.1
Version: 5.0
Action: UPDATE
Handle: DENIC-1000022-EXAMPLE-PERSON
Type: PERSON
Name: John Doe
PostalCode: 60596
City: Frankfurt
CountryCode: DE
EMail: john.doe@denic.de
Phone: +49.69272350
Address: NISserverHold
Version: 5.0
Action: UPDATE
Handle: DENIC-1000022-EXAMPLE-PERSON
Type: PERSON
Name: John Doe
PostalCode: 60596
City: Frankfurt
CountryCode: DE
EMail: john.doe@denic.de
Phone: +49.69272350
Address: NISconnect
Version: 5.0
Action: UPDATE
Handle: DENIC-1000022-EXAMPLE-PERSON
Type: PERSON
Name: John Doe
PostalCode: 60596
City: Frankfurt
CountryCode: DE
EMail: john.doe@denic.de
Phone: +49.69272350
Address: NISverificationRequired
Version: 5.0
Action: UPDATE
Handle: DENIC-1000022-EXAMPLE-PERSON
Type: PERSON
Name: John Doe
PostalCode: 60596
City: Frankfurt
CountryCode: DE
EMail: john.doe@denic.de
Phone: +49.69272350
Address: NISserverHold
Version: 5.0
Action: UPDATE
Handle: DENIC-1000022-EXAMPLE-PERSON
Type: PERSON
Name: John Doe
PostalCode: 60596
City: Frankfurt
CountryCode: DE
EMail: john.doe@denic.de
Phone: +49.69272350
Address: NISdelete